-<summary>Fixed an error in the calculation of effective rate limit from multiple policies</summary>
+<summary>Fixed an error in the calculation of effective rate limit from multiple policies. This change may affect existing configurations by applying a different rate limit.</summary>
 

 {{< note success >}}
 **Note**  
-Prior to Tyk 5.4.0 there was a long-standing bug in the calculation of the effective rate limit applied to the key where Tyk would combine the highest `rate` and highest `per` from the policies applied to the key, so for the example above the key would have `rate` set to 100 and `per` set to 30 giving an effective rate limit of 3.33rps. This has now been corrected.
+Prior to Tyk 5.4.0 there was a long-standing bug in the calculation of the effective rate limit applied to the key where Tyk would combine the highest `rate` and highest `per` from the policies applied to the key, so for the example above the key would have `rate` set to 100 and `per` set to 30 giving an effective rate limit of 3.33rps. This has now been corrected. For more details, see the [release notes](link-to-the-specific-release-notes).
 {{< /note >}}
 

-Note that this corrected logic is applied when access keys are presented in API requests. If you are applying multiple policies to keys, there may be a change in the effective rate limit when using Tyk 5.4.0 compared with pre-5.4.0 versions.
+Note that this corrected logic is applied when access keys are presented in API requests and is backward compatible. Users applying multiple policies to keys should review their configurations to ensure desired operation under the new logic. There may be a change in the effective rate limit when using Tyk 5.4.0 compared with pre-5.4.0 versions.
 

-With the fix applied in Tyk 5.4.0, the Gateway will now apply the highest effective rate to the key - so in this example, the key would take the rate limit from policy B: `rate = 100` and `per = 10` (10rps).
+With the fix applied in Tyk 5.4.0, the Gateway now correctly applies the highest effective rate limit. For example, if policy A has a rate limit of 3rps and policy B has 10rps, the key will use the 10rps from policy B, avoiding the previous error of incorrectly combining the highest `rate` and `per` values.